home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20000217-20000824
/
000408_news@columbia.edu _Fri Jul 14 10:10:35 2000.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from watsun.cc.columbia.edu (watsun.cc.columbia.edu [128.59.39.2])
by fozimane.cc.columbia.edu (8.9.3/8.9.3) with ESMTP id KAA07693
for <kermit.misc@cpunix.cc.columbia.edu>; Fri, 14 Jul 2000 10:10:35 -0400 (EDT)
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.59.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id KAA01395
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 14 Jul 2000 10:10:34 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.9.3/8.9.3) id JAA18983
for kermit.misc@watsun.cc.columbia.edu; Fri, 14 Jul 2000 09:54:24 -0400 (EDT)
X-Authentication-Warning: newsmaster.cc.columbia.edu: news set sender to <news> using -f
From: fdc@columbia.edu (Frank da Cruz)
Subject: Re: Suggestion for Kermit script language
Date: 14 Jul 2000 13:54:23 GMT
Organization: Columbia University
Message-ID: <8kn62f$ih5$1@newsmaster.cc.columbia.edu>
To: kermit.misc@columbia.edu
In article <8km7ci$941$1@newsmaster.cc.columbia.edu>,
Jeffrey Altman <jaltman@watsun.cc.columbia.edu> wrote:
: In article <396E9035.C028E5FE@value.net>,
: Mark Sapiro <msapiro@value.net> wrote:
: : Often in a macro or script one wishes to save the current settings of
: : certain parameters before changing them so that they can be restored
: : later. When the setting is reflected in a variable, this can be done,
: : but it is a bit awkward. Some settings are not reflected in variables,
: : and saving a prior setting can't be done.
:
: I think that Frank and I would love to do this just like we would
: love to have a SAVE command for every feature set. But it is a lot
: of work. There are simply thousands of commands in Kermit.
:
Right. Add a feature like this in all its glory (a variable for every
setting) and n people are happy and n*n people howl in agony at the
resulting program bloat.
In a pinch, for any setting that can't be queried programatically, you
can always make your own variable and set it whenever you give the
corresponding SET command.
By the way, certain settings are on the stack, and therefore save and
restore themselves automatically whenever you enter/leave a macro or
command file:
SET QUIET { ON, OFF }
SET { MACRO, TAKE } ERROR { ON, OFF }
SET INPUT TIMEOUT { PROCEED, QUIT }
SET INPUT CASE { IGNORE, OBSERVE }
SET COUNT (a relic from from the early days)
- Frank